Fixes the "no documentation" state on pkg.go.dev.

Why the page was empty

Not an indexing or license problem — there genuinely was no documentation. go doc . returned nothing.

The module root is package main, and the only comment above the package clause is the SPDX header:

// Copyright (c) 2025-2026 Netresearch DTT GmbH
// SPDX-License-Identifier: MIT
                              ← blank line
package main

Go treats a comment block as package documentation only when it is immediately adjacent to the package clause. The blank line separates it, so there was no doc comment. (The blank line is correct — without it pkg.go.dev would render the copyright header as the package description.)

Nine of fifteen packages were in that state: the root plus cli, config, core, metrics, middlewares, static, test, web. The packages added more recently (core/adapters/*, core/domain, core/ports, core/persist, test/testutil) already had comments.

What this changes

A doc.go per undocumented package, describing what it actually does rather than restating its name. The root one doubles as the command's documentation, which is what pkg.go.dev renders for a command module:

Ofelia is a job scheduler for Docker hosts, and a replacement for cron in
container environments. Jobs are declared in an INI file, through labels on the
containers themselves, or at runtime through the web API, and run either inside
an existing container, in a fresh one, on the host, or as a Swarm service.
...

Making it stick

Documentation that nothing enforces drifts back, which is how this happened: revive's package-comments rule was already in .golangci.yml — explicitly disabled: true.

Enabling it was not enough. The rule stayed silent because the comments exclusion preset filtered it out. Removing that preset makes the rule effective, but also surfaces 50 findings about missing comments on exported symbols — a separate and much larger question. So the exported-symbol rule keeps its current exemption through a targeted exclusion (text: '^exported: '), and only the package-comment requirement becomes blocking.

Net config change is three lines:

       - name: package-comments
-        disabled: true
...
-      - comments
+      - linters:
+          - revive
+        text: '^exported: '

Verification

Enforcement proven in both directions, not assumed:

Also: go doc . now returns the command documentation; go list -f '{{.Doc}}' ./... reports a synopsis for all 15 packages; build and vet clean under the default and integration tags; go test -race ./... 14/14.

Note that pkg.go.dev will still show the previous release until a tag containing this lands — the page currently serves v0.27.0 and has not yet picked up v0.28.0.